Service processing method and apparatus

ABSTRACT

Implementations of the present specification provide a service processing method. The method is performed by a service platform, the service platform including multiple area sites corresponding to multiple service areas, and each area site including a corresponding buyer service site and seller service site. The method includes: splitting a whole-order service into a buyer service and a seller service; further, on one hand, routing the buyer service to a buyer service site in a service area that a corresponding buyer belongs to, for the buyer service site to process the buyer service through interconnection with the buyer based on an area user identifier, and to locally store processed data, where the area user identifier is determined based on multiple area identities associated with a domain-wide identity corresponding to the buyer; and on the other hand, routing the seller service to a seller service site in a service area that a corresponding seller belongs to, for the seller service site to process the seller service through interconnection with the seller, and to locally store processed data.

BACKGROUND Technical Field

Implementations of the present specification relate to the field ofcomputer technologies, and in particular, to a service processing methodand apparatus.

Description of the Related Art

In the current trend of internationalization, to better meet userrequirements, many service platforms develop cross-country orcross-region services, so that platform users in different countries orregions can implement service transactions through the serviceplatforms. For example, Chinese buyers can purchase products provided bysellers in other countries or regions. In addition, in the current bigdata era, data security is particularly important. Most countries andregions propose data security-related regulatory requirements. Inaddition, different countries or regions have different compliancerequirements for service data. For example, some countries require thatuser data generated in their territories cannot be stored abroad, andothers require that user data generated in their territories cannot bestored in blacklisted countries that are specified by the countries.

To enable cross-domain services developed by the service platform tomeet differentiated data regulatory requirements of various countries,it is common practice in the industry to physically isolate services indifferent countries or regions. For example, a certain service platformestablishes country sites in two countries respectively, and deploymentand data storage of each site is totally isolated. Such practice causesinconvenience to platform users. For example, if a Chinese buyer wantsto use services provided by country sites other than a Chinese site, thebuyer needs to re-register accounts with the other country sites, or ifa Chinese seller wants to provide products sold by the seller to othercountry sites, the seller needs to re-sign up with the other countrysites.

BRIEF SUMMARY

Implementations of the present specification describe a serviceprocessing method and apparatus, which can effectively simplify anoperation process of a user on a service platform while meetingdifferentiated data regulatory requirements of different places, so asto optimize user experience.

According to a first aspect, a service processing method is provided.The method is performed by a service platform, the service platformincludes multiple area sites corresponding to multiple service areas,and each area site includes a corresponding buyer service site andseller service site; and the method includes: receiving a paymentrequest initiated by a first buyer for a first order, the first buyercorresponding to a first domain-wide user identifier, a product in thefirst order being provided by a first seller, and the payment requestincluding a selected payment channel; determining a first service areathat a buyer payment service corresponding to the payment requestbelongs to, a first area site corresponding to the first service areaincluding a first buyer service site, the first buyer having a firstarea user identifier in the first service area, which is determinedbased on multiple area user identifiers associated with the firstdomain-wide user identifier, and a place of registration of a paymentinstitution corresponding to the payment channel being located in thefirst service area; routing the buyer payment service to the first buyerservice site, for the first buyer service site to process the buyerpayment service through interconnection with the payment channel andinterconnection with the first buyer based on the first area useridentifier, and to locally store service data generated by theprocessing the buyer payment service; obtaining a payment successmessage corresponding to the payment request; determining that ato-be-processed seller delivery service belongs to a second service areabased on the payment success message, a place of registration of thefirst seller being located in the second service area, and a second areasite corresponding to the second service area including a second sellerservice site; and routing the seller delivery service to the secondseller service site, for the second seller service site to process theseller delivery service through interconnection with the first seller,and to locally store service data generated by the processing the sellerdelivery service.

In an implementation, before the receiving the payment request initiatedby the first buyer for the first order, the method further includes:determining the first domain-wide user identifier corresponding to thefirst buyer in response to a successful login of the first buyer; andcreating the first order in response to receiving an order creationrequest initiated by the first buyer based on the product.

In an implementation, the determining the first domain-wide useridentifier corresponding to the first buyer includes: obtaining a username of the first buyer; and performing a hash operation on the username to obtain the first domain-wide user identifier; or querying thefirst domain-wide user identifier based on a pre-established mappingrelationship between a user name and a domain-wide user identifier.

In an implementation, after the creating the first order and before thereceiving the payment request initiated by the first buyer for the firstorder, the method further includes: obtaining location elementinformation of the first buyer; determining a service area in which thefirst buyer is currently located based on the location elementinformation, and using the service area as the first service area;determining the first area user identifier of the first buyer in thefirst service area based on the multiple area user identifierscorresponding to multiple service areas; and obtaining multiplecandidate payment channels for selection by the first buyer, whereplaces of registration of payment institutions corresponding to themultiple candidate payment channels are all located in the first servicearea.

Further, in an implementation, the location element information includesat least one of longitude and latitude information, a network address,an Internet Protocol (IP) address, and a consignee address included inthe first order.

In an implementation, the determining the first area user identifier ofthe first buyer in the first service area based on the multiple areauser identifiers corresponding to the multiple service areas includes:creating a new user identifier as the first area user identifier when auser identifier corresponding to the first service area does not existin the multiple area user identifiers; and classifying the first areauser identifier into the multiple area user identifiers.

In an implementation, the determining the first service area that thebuyer payment service corresponding to the payment request belongs toincludes: determining a place of registration corresponding to thepayment channel, and using a service area in which the place ofregistration is located as the first service area.

In an implementation, after the determining the first service area thatthe buyer payment service corresponding to the payment request belongsto, and before the routing the buyer payment service to the first buyerservice site, the method further includes: determining the first areauser identifier of the first buyer in the first service area based onthe multiple area user identifiers corresponding to multiple serviceareas.

In an implementation, the determining the second service area theto-be-processed seller delivery service belongs to based on the paymentsuccess message includes: determining a place of registration of thefirst seller based on the payment success message, and using a servicearea in which the place of registration is located as the second servicearea.

In an implementation, after the routing the seller delivery service tothe second seller service site, the method further includes: routing anorder settlement service corresponding to the first seller to the secondseller service site, for the second seller service site to process theorder settlement service through interconnection with the second seller,and to locally store service data generated by the processing the ordersettlement service.

In an implementation, the multiple service areas correspond to multiplearea sites, and after the routing the seller delivery service to thesecond seller service site, the method further includes: in response toan order viewing instruction sent by the first buyer, querying orderinformation of multiple orders associated with the multiple area useridentifiers from the multiple area sites for viewing by the first buyer,where the multiple orders include the first order.

In an implementation, the multiple service areas correspond to multiplearea sites, and before the receiving the payment request initiated bythe first buyer for the first order, the method further includes:querying multiple historical orders associated with the multiple areauser identifiers from the multiple area sites; and recommending aproduct to the first buyer based on purchased products included in themultiple historical orders.

According to a second aspect, a service processing method is provided.The method is performed by a service platform, the service platformincludes multiple area sites corresponding to multiple service areas,and each area site includes a corresponding seller service site andbuyer service site; and the method includes: determining that a firstservice currently needs to be processed; in response to determining thatthe first service needs to be processed through interconnection with afirst buyer, determining a first buyer service site corresponding to afirst service area that the first buyer belongs to, the first buyercorresponding to a first domain-wide user identifier and having a firstarea identity in the first service area, which is determined based onmultiple area user identifiers associated with the first domain-wideuser identifier; routing the first service to the first buyer servicesite, for the first buyer service site to process the first servicethrough interconnection with the first buyer based on the first areauser identifier, and to locally store service data generated by theprocessing the first service; in response determining that the firstservice needs to be processed through interconnection with a firstseller, determining a second seller service site corresponding to asecond service area that the first seller belongs to, a place ofregistration of the first seller being located in the second servicearea; and routing the first service to the second seller service site,for the second seller service site to process the first service throughinterconnection with the first seller, and to locally store service datagenerated by the processing the first service.

In an implementation, the first service is a buyer payment service, andthe determining that a first service currently needs to be processedincludes: determining that the buyer payment service currently needs tobe processed in response to a payment request initiated by the firstbuyer for a first order, where the payment request includes a selectedpayment channel; in response to determining that the first service needsto be processed through interconnection with the first buyer,determining the first buyer service site corresponding to the firstservice area that the first buyer belongs to includes: determining,based on predetermined multiple buyer services that need to interconnectwith buyers, that the multiple buyer services include the buyer paymentservice; and determining the first buyer service site corresponding tothe first service area that the first buyer belongs to, where a place ofregistration of a payment institution corresponding to the paymentchannel is located in the first service area; and the routing the firstservice to the first buyer service site, for the first buyer servicesite to process the first service through interconnection with the firstbuyer based on the first area user identifier, and locally store theservice data generated by the processing the first service, includes:routing the buyer payment service to the first buyer service site, forthe first buyer service site to process the buyer payment servicethrough interconnection with the payment channel and interconnectionwith the first buyer based on the first area user identifier, and tolocally store service data generated by the processing the buyer paymentservice.

In an implementation, the first service is a seller delivery service,and the determining that a first service currently needs to be processedincludes: determining that the seller delivery service currently needsto be processed in response to a payment success message for a firstorder, where the first order includes a product provided by the firstseller; and in response determining that the first service needs to beprocessed through interconnection with the first seller, determining thefirst seller service site corresponding to the first service area thatthe first seller belongs to includes: determining, based onpredetermined multiple seller services that need to interconnect withsellers, that the multiple seller services include the seller deliveryservice.

According to a third aspect, a service processing apparatus is provided.The apparatus is integrated into a service platform, the serviceplatform includes multiple area sites corresponding to multiple serviceareas, and each area site includes a corresponding buyer service siteand seller service site; and the apparatus includes: a payment requestreceiving unit, configured to receive a payment request initiated by afirst buyer for a first order, the first buyer corresponding to a firstdomain-wide user identifier, a product in the first order being providedby a first seller, and the payment request including a selected paymentchannel; a first area determining unit, configured to determine a firstservice area that a buyer payment service corresponding to the paymentrequest belongs to, a first area site corresponding to the first servicearea including a first buyer service site, the first buyer having afirst area user identifier in the first service area, which isdetermined based on multiple area user identifiers associated with thefirst domain-wide user identifier, and a place of registration of apayment institution corresponding to the payment channel being locatedin the first service area; a payment service routing unit, configured toroute the buyer payment service to the first buyer service site, for thefirst buyer service site to process the buyer payment service throughinterconnection with the payment channel and interconnection with thefirst buyer based on the first area user identifier, and to locallystore service data generated by the processing the buyer paymentservice; a payment success acquisition unit, configured to obtain apayment success message corresponding to the payment request; a secondarea determining unit, configured to determine that a to-be-processedseller delivery service belongs to a second service area based on thepayment success message, a place of registration of the first sellerbeing located in the second service area, and a second area sitecorresponding to the second service area including a second sellerservice site; and a delivery service routing unit, configured to routethe seller delivery service to the second seller service site, for thesecond seller service site to process the seller delivery servicethrough interconnection with the first seller, and to locally storeservice data generated by the processing the seller delivery service.

According to a fourth aspect, a service processing apparatus isprovided. The apparatus is integrated into a service platform, theservice platform includes multiple area sites corresponding to multipleservice areas, and each area site includes a corresponding sellerservice site and buyer service site; and the apparatus includes: aservice determining unit, configured to determine that a first servicecurrently needs to be processed; a buyer site determining unit,configured to: in response to determining that the first service needsto be processed through interconnection with a first buyer, determininga first buyer service site corresponding to a first service area thatthe first buyer belongs to, the first buyer corresponding to a firstdomain-wide user identifier and having a first area identity in thefirst service area, which is determined based on multiple area useridentifiers associated with the first domain-wide user identifier; abuyer service routing unit, configured to route the first service to thefirst buyer service site, for the first buyer service site to processthe first service through interconnection with the first buyer based onthe first area user identifier, and to locally store service datagenerated by the processing the first service; a seller site determiningunit, configured to: in response to determining that the first serviceneeds to be processed through interconnection with a first seller,determining a second seller service site corresponding to a secondservice area that the first seller belongs to, a place of registrationof the first seller being located in the second service area; and aseller service routing unit, configured to route the first service tothe second seller service site, for the second seller service site toprocess the first service through interconnection with the first seller,and to locally store service data generated by the processing the firstservice.

According to a fifth aspect, a computer-readable storage medium storingcomputer programs is provided. A computer performs the method accordingto the first aspect or the second aspect when the computer programs areexecuted on the computer.

According to a sixth aspect, a computing device is provided, including amemory and a processor. The memory stores executable code, and theprocessor implements the method according to the first aspect or thesecond aspect when executing the executable code.

In conclusion, according to the service processing method disclosed inthe implementations of the present specification, a user can useservices provided by global sellers by registering with a serviceplatform only once while it is ensured that service data meetsregulatory constraints, and a seller and a payment channel can be reusedby global users or global buyers by accessing the service platform onlyonce. As such, this can undoubtedly improve user experience greatly andeffectively promote service development.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To describe the technical solutions in multiple implementationsdisclosed in the present specification more clearly, the followingbriefly describes the accompanying drawings for illustrating suchimplementations. Clearly, the accompanying drawings described below aremerely multiple implementations disclosed in the present specification,and a person of ordinary skill in the art can derive other drawings fromsuch accompanying drawings without making innovative efforts.

FIG. 1 is a schematic diagram illustrating association of a domain-wideuser identity with area identities according to an example;

FIG. 2 is a schematic diagram illustrating deployment of logical sitesaccording to an implementation;

FIG. 3 is a schematic architectural diagram illustrating a scenariowhere a user uses a domain-wide service according to an implementation;

FIG. 4 is a schematic flowchart illustrating a service processing methodaccording to an implementation;

FIG. 5 is a schematic flowchart illustrating a service processing methodaccording to another implementation;

FIG. 6 is a schematic structural diagram illustrating a serviceprocessing apparatus according to an implementation; and

FIG. 7 is a schematic structural diagram illustrating a serviceprocessing apparatus according to another implementation.

DETAILED DESCRIPTION

The following describes multiple implementations disclosed in thepresent specification with reference to the accompanying drawings.

As mentioned above, to meet different regulatory requirements of variouscountries, it is common practice in the industry to physically isolateservices in different countries or regions. For example, a certainservice platform (e.g., an e-commerce platform) establishes countrysites in two countries respectively, and domain names, account systems,system deployment, and data storage of these two country sites aretotally isolated.

Although such practice can meet regulatory constraints, user experienceand service development are affected. For example, if a person wants touse services in two country sites established on a certain serviceplatform, the user needs to register accounts in the two country sitesrespectively. In this case, the same person has two platform accounts.However, because account systems of the two country sites are totallyisolated and not connected, user data corresponding to the two platformaccounts is also isolated, which affects user experience. Therefore, theuser needs to register repeatedly, and operations are cumbersome. Inaddition, in one country site established on the platform, the usercannot view a purchase record of the user in the other country site.Furthermore, personalized recommendation such as platform friendrecommendation and product recommendation can only be performed based oneach site because user data is isolated, which causes limited accuracyof the recommendation result and limited user experience, and restrictsservice development.

In addition, two country sites are independent of each other. If aseller or a payment institution wants to develop services in the twocountry sites, the seller or the payment institution needs to sign upwith the two country sites respectively. Therefore, the servicemotivation of the seller and the payment institution is reduced. Inaddition, the number of sellers and payment institutions accessing theservice platform is limited, affecting user experience in the serviceplatform. In addition, payment channels provided by the seller and thepayment institution have high access costs and low reusability, whichalso restricts service development.

Based on this, the inventors propose a service processing method, whichis particularly applicable to cross-domain services. According to theservice processing method, a user can use services provided by globalsellers only by registering with a service platform once while it isensured that service data meets regulatory constraints, and a seller anda payment channel can be reused by global users or global buyers only byaccessing the service platform once. As such, this can undoubtedlyimprove user experience greatly and effectively promote servicedevelopment.

To implement the previously described service processing method, theinventors propose techniques in the following two aspects:

In one aspect, a domain-wide platform user model is established,including a global user identifier (or referred to as an area-wide useridentifier or a domain-wide user identifier) of each user and an areauser identifier of each user in each country or region. For example,FIG. 1 shows domain-wide user identifier A of user A included in thedomain-wide platform user model and area user identifiers of user A in N(N is a positive integer) areas, for example, including area useridentifier A₁ in area 1 (an area numbered 1), etc.

It should be noted that because a user is usually a natural person, andis an independent, free and mobile individual, data generated by theuser is usually regulated by a region where the data is generated. Amajor matter of the regulation is to restrict a storage place of thedata. For example, a certain country requires user data generated in thecountry only be allowed to be stored in the country, but usually doesnot restrict normal and compliant access to the data regulated by thecountry.

The domain-wide platform user model established above is an associationrelationship between some identifiers, which does not violate a dataregulatory rule because the model does not include user-sensitiveinformation. In addition, a user identifier can be automaticallygenerated after the service platform identifies the same user indifferent regions, without requiring the user to register repeatedly andeven without awareness of the user, thereby reducing user operations. Inaddition, through the domain-wide platform user model, user datagenerated by the same user in different regions can be connected.Therefore, regardless of which region the user is located in, the usercan be provided with services based on full data of the user around theworld, thereby greatly improving user experience.

In the other aspect, considering main characteristics of cross-domainservices are that a buyer and a seller belong to different regions anddata regulation requirements of different regions are different, logicalsites are designed for each country and region, and the logical sitesare classified into buyer service sites for processing buyer servicesand seller service sites for processing seller services. Based on this,the cross-domain services can be divided into buyer services and sellerservices. Based on a region that the buyer service belongs to, the buyerservice is routed to a buyer service site in the corresponding region,for the site to process the buyer services, and to locally storegenerated buyer service data. Similarly, based on another region thatthe seller service belongs to, the seller service is routed to a sellerservice site in the another region, for the site to process the sellerservice, and to locally store generated seller service data. It shouldbe understood that a site is a storage area, which can store serviceexecution logic, service data, etc. The logical site means a separatelogical site, not a totally isolated physically site. The logical sitecan provide normal, compliant, and legal data access services for othersites or platforms.

For example, FIG. 2 shows multiple logical sites (or referred to asmultiple area sites) corresponding to multiple regions. Each logicalsite includes a buyer service site and a seller service site, and aservice routing module illustrated is configured to route a buyerservice and a seller service included in cross-domain services to acorresponding buyer service site and seller service site respectively.

It should be noted that determining a home location of a seller servicemainly depends on a region that a seller in the seller service belongsto. Before providing a service, the seller usually needs to registerwith the related department, and a region where a place of registrationof the seller is located has jurisdiction over the seller. Therefore,the region that the seller belongs to can be determined based on theplace of registration of the seller, and further, the region that theseller in the seller service belongs to is used as the home location ofthe seller service.

In addition, similar to the seller, a payment channel has a naturalidentity. The natural identity of the payment channel is a place ofregistration of a payment institution behind the payment channel. Thepayment channel is mainly related to a buyer payment service. When abuyer uses a service provided by the seller through the serviceplatform, the buyer needs to pay for the service. In this case,selection of the payment channel is involved. Therefore, in the buyerpayment service, a home location of the payment channel and a regionwhere the buyer is located can be comprehensively considered todetermine a region corresponding to the buyer payment service, forrouting the buyer payment service.

For example, for ease of intuitive understanding, FIG. 3 shows ascenario where global services are provided for user A based on adomain-wide identity and area identities of user A. Buyer service site 1interconnects with a buyer service of user A based on area identity A₁.In addition, N (N is a positive integer) buyer service sitescorresponding to N areas respectively interconnect with local paymentchannels, and corresponding N seller service sites respectivelycorrespond to local sellers. As such, the seller and the payment channel(or the payment institution behind the payment channel) can provideservices to global buyers by signing up with the service platform onlyonce.

The above mainly describes an inventive concept of the serviceprocessing method proposed by the inventors as described herein. Thefollowing describes implementation steps of the service processingmethod with reference to example implementations.

For example, FIG. 4 is a schematic flowchart illustrating a serviceprocessing method according to an implementation. The service processingmethod is performed by a service platform. For example, the serviceplatform includes multiple area sites corresponding to multiple serviceareas, and each area site includes a corresponding buyer service siteand seller service site.

With respect to the above service platform, in an implementation, theservice platform can be implemented as a server cluster or a devicecluster. In an implementation, the service platform can be an e-commerceplatform, a network transaction platform, etc. The service platformallows service providers (sellers) to reside to provide services orproducts for users in the service platform. It should be noted that theservices and the products in the present specification can be consideredas equivalent, and refer to services and products in a broad sense. Inan implementation, the product (or service) can be a physical product(e.g., a mobile phone), a virtual product (e.g., an e-book, a videocourse, and a music resource), a consulting service, etc.

With respect to the above multiple service areas, any one of these areascan be a separate country or region or a separate geographical rangedivided based on the regulatory rule. For example, if several countriesreach an agreement to agree on data sharing or cooperative regulation,these countries can be classified into the same service area. It shouldbe understood that the multiple service areas are mutually exclusive,that is, geographical ranges do not overlap. In addition, the serviceplatform can determine, based on the development scale and the servicecapability of the service platform, a country, a region, or a city wherethe service platform can develop services, and further obtain multipleservice areas through division based on service coverage and theexisting data regulatory rule of the service platform. In addition,because the multiple area sites corresponding to the multiple serviceareas are logical sites, the multiple area sites can be flexiblyadjusted later based on the service development situation and the changeof the data regulatory rule.

With respect to the above multiple area sites, the multiple area sitescorrespond to multiple service areas, and each area site corresponds toone service area, and is configured to interconnect with and processservices that belong to the corresponding service area. For thedescription of the area site, references can also be made to the abovedescription of the logical site and the site. Details are omitted hereinfor simplicity.

With respect to the buyer service site and the seller service siteincluded in each area site, the buyer service site is configured tointerconnect with and process local (the region corresponding to thebuyer service site) buyer services, and the seller service site isconfigured to interconnect with and process local seller services. Forthe description of the buyer service site and the seller service site,references can also be made to the above description of the buyerservice site and the seller service site.

The above describes the area sites, the buyer service site, and theseller service site included in the service platform. Based on thesesites, the previously described service processing method can beimplemented. As shown in FIG. 4, the service processing method includesthe following steps:

Step S410: Receive a payment request initiated by a first buyer for afirst order. The first buyer corresponds to a first domain-wide useridentifier, a product in the first order is provided by a first seller,and the payment request includes a selected payment channel. Step S420:Determine a first service area that a buyer payment servicecorresponding to the payment request belongs to. A first area sitecorresponding to the first service area includes a first buyer servicesite, the first buyer has a first area user identifier in the firstservice area, which is determined based on multiple area useridentifiers associated with the first domain-wide user identifier, andthe multiple area user identifiers correspond to multiple service areas.A place of registration of a payment institution corresponding to thepayment channel is located in the first service area. Step S430: Routethe buyer payment service to the first buyer service site, for the firstbuyer service site to process the buyer payment service throughinterconnection with the payment channel and interconnection with thefirst buyer based on the first area user identifier, and to locallystore service data generated by the processing the buyer paymentservice. Step S440: Obtain a payment success message corresponding tothe payment request. Step S450: Determine that a to-be-processed sellerdelivery service belongs to a second service area based on the paymentsuccess message. A place of registration of the first seller is locatedin the second service area, and a second area site corresponding to thesecond service area includes a second seller service site. Step S460:Route the seller delivery service to the second seller service site, forthe second seller service site to process the seller delivery servicethrough interconnection with the first seller, and to locally storeservice data generated by the processing the seller delivery service.

For the previously described steps, first, it should be noted that“first” in “first buyer,” “first order,” etc., and “second” in “secondservice area,” etc., are used for clarity of description, and are usedto distinguish between the same type of things, without otherrestrictive functions such as sorting.

The previously described steps are, for example, further illustrated asfollows:

First, in step S410, the payment request initiated by the first buyerfor the first order is received. The first buyer corresponds to thefirst domain-wide user identifier, the product in the first order isprovided by the first seller, and the payment request includes theselected payment channel. It should be noted that the first buyer can beany user who uses the service platform, the first order can be any ordersubmitted by the first buyer, and the first seller can be any one ofservice providers that reside in the service platform.

With respect to determining the above first domain-wide user identifier,in an implementation, before step S410, the method can include:determining the first domain-wide user identifier corresponding to thefirst buyer in response to the login success operation of the firstbuyer. In an example implementation, the determining the firstdomain-wide user identifier can include: obtaining a login user namecorresponding to the login success operation, and then performing a hashoperation on the login user name to obtain the first domain-wide useridentifier. It should be understood that there is a one-to-onecorrespondence between raw data and encrypted data obtained after thehash operation is performed on the raw data. Therefore, there is aone-to-one mapping relationship between domain-wide user identifiersobtained in this way and login accounts, so that users can be uniquelyidentified securely and reliably. In an example implementation, thedetermining the first domain-wide user identifier can further include:obtaining a login user name corresponding to the login successoperation, and then querying the first domain-wide user identifiercorresponding to the login user name based on a pre-established mappingrelationship between a user name and a domain-wide user identifier. Inan example implementation, the determining the first domain-wide useridentifier can also include: determining an area user identifiercorresponding to the login user name in a place of registration of thelogin user name from registration information stored in the multiplearea sites based on the login user name, and then determining, based onthe domain-wide platform user model, a domain-wide user identifiercorresponding to the area user identifier, namely, the first domain-wideuser identifier.

In addition, in addition to being triggered by the logic successoperation, determining the first domain-wide user identifier can betriggered by other operations performed after the login success, forexample, a tap operation on the product's picture, a submit operation onthe order, or a payment operation on the order. In addition, the firstdomain-wide user identifier can be alternatively determined when thereis no login. In an example implementation, after receiving a platformaccess request (the user opens the service platform interface), theservice platform can obtain a Media Access Control (MAC) address of adevice that sends the access request, and then determine a correspondingdomain-wide user identifier, namely, the first domain-wide useridentifier, based on a pre-established mapping relationship between aMAC address and a domain-wide user identifier.

In an implementation, the first domain-wide user identifier can begenerated when the user registers a platform account. During an exampleimplementation, for a new account registered successfully, a domain-wideuser identifier corresponding to the new account can be generated byusing a hash operation, or a data sequence can be generated by using arandom algorithm as a new domain-wide user identifier, and a mappingrelationship between the new account and the new domain-wide useridentifier is established. In another implementation, the firstdomain-wide user identifier can be generated when the user operates theservice platform. In an example implementation, after receiving theplatform access request, the service platform can obtain the MAC addressof the device that sends the access request, and then search theestablished mapping relationship between a MAC address and a domain-wideuser identifier for whether the MAC address of the device is included.If the MAC address does not exist, the service platform generates a newdomain-wide user identifier corresponding to the MAC address, andupdates the mapping relationship by using the new domain-wide useridentifier.

The above describes determining and generating the first domain-wideuser identifier.

In addition, with respect to creating the first order, in animplementation, the order creation service can be completed by theservice platform. Further, in an example implementation, the serviceplatform can send service data of the order creation service to thebuyer service site in the service area the first buyer belongs to. Itshould be noted that when the user gives up payment for the first order,or when the user cancels the first order without paying for the firstorder, the service platform can discard service data of the first order.

Correspondingly, this step can include: receiving, by the serviceplatform, the payment request from a user terminal used by the firstbuyer. It should be understood that the user uses, by using the userterminal (e.g., a smartphone or a tablet), a user interaction interfaceor a platform APP provided by the service platform.

In an implementation, the order creation service can be, for example,completed by the buyer service site in the service area the first buyerbelongs to. For example, in response to an example operation of thefirst buyer on the service platform, a buyer service before orderpayment corresponding to the first buyer can be routed to a buyerservice site in an area where the first buyer is located. The exampleoperation can include a login operation, a login success operation, apage scrolling operation, a picture tap operation, an order submissionoperation, etc. The buyer service before order payment can include aplatform login service, an interface browsing service, an order creationservice, etc. In an example implementation, the area where the firstbuyer is located needs to be determined before order payment is routedto the buyer service site in the area where the first buyer is located.The area can be determined based on location element information of thefirst buyer obtained in real time. For example, the location elementinformation of the first buyer can be obtained in response to thespecified operation, to determine a third service area where the firstbuyer is currently located. In an example implementation, the locationelement information can include longitude and latitude information, anetwork address, an Internet Protocol (IP) address, a logisticsconsignee address of the first buyer, or a logistics consignor addressuploaded by the user terminal. Therefore, the third service area wherethe user is currently located can be determined so as to route the ordercreation service to a third buyer service site in the correspondingthird area site.

Correspondingly, this step can include: receiving, by the serviceplatform from the third buyer service site, the payment requestinitiated by the first buyer for the first order.

As described herein, the payment request initiated by the first buyerfor the first order can be received. In addition, the product in thefirst order is provided by the first seller, and the payment requestincludes the payment channel selected by the first buyer. Based on this,next, in step S420, it is determined that the to-be-processed buyerpayment service belongs to the first service area based on the paymentrequest.

As described herein, the buyer payment service involves the user and thepayment channel. A service area where the user is located and a servicearea where a place of registration of a payment institutioncorresponding to the payment channel is located may be the same ordifferent. When the service areas are the same, the corresponding commonservice area can be used as the first service area the buyer paymentservice belongs to. When the service areas are different, one of the twodifferent service areas can be determined as the first service areabased on the guidance of the data regulatory requirement or negotiationresults between the service platform and data regulatory institutions indifferent service regions. Based on this, there are multipleimplementations for this step.

In an implementation, the service area the buyer payment service belongsto can be determined from the perspective of the service area where thefirst buyer is located. In an implementation, before step S410, themethod can further include: obtaining location element information ofthe first buyer; determining a third service area where the first buyeris currently located based on the location element information; and thenobtaining multiple candidate payment channels (e.g., Yu'e Bao payment,online bank payment of a certain bank, and e-wallet payment) based onthe third service area for selection by the first buyer.

In an example implementation, places of registration of paymentinstitutions (e.g., Huabei payment, Yu'e Bao payment, or online bankpayment of a certain bank) corresponding to the multiple candidatepayment channels are all located in the third service area (e.g.,China). Therefore, a place of registration corresponding to the paymentchannel selected from the multiple candidate payment channels iscertainly also located in the third service area. Correspondingly, thisstep can include: determining the third service area as the service areathe buyer payment service belongs to. In this case, the first servicearea is equivalent to the third service area.

In an example implementation, service areas where multiple places ofregistration corresponding to the multiple candidate payment channelsare located can be service areas allowing service data (including buyerpayment service data) locally generated to be stored in the thirdservice area. This means that the service areas corresponding to themultiple candidate payment channels can include the third service area,or can include other service areas. Regardless of which payment channelis selected by the user, storing the buyer payment service data in thethird service area meets the data regulatory requirement.Correspondingly, this step can still include: determining the thirdservice area as the service area the buyer payment service belongs to.In this case, the first service area is still equivalent to the thirdservice area.

In an implementation, the service area the buyer payment service belongsto can be determined from the perspective of the service area where theplace of registration of the payment institution corresponding to thepayment channel is located. In an implementation, this step can include:querying the place of registration corresponding to the selected paymentchannel, and then determining the service area where the place ofregistration is located as the first service area the buyer paymentservice belongs to. In this case, the first service area may be the sameas the third service area. If the first service area is different fromthe third service area, if the data regulatory requirement of the thirdservice area allows service data of the third service area to be storedin the first service area, it is acceptable to attribute the buyerpayment service into the first service area, or if the data regulatoryrequirement does not allow data to be exported, negotiation can beperformed, or the previously described implementation of determining thefirst service area from the user's perspective is used.

In addition, the first buyer has the first area user identifier in thefirst service area, the first area user identifier is determined basedon the multiple area user identifiers associated with the firstdomain-wide user identifier, and the multiple area user identifierscorrespond to the multiple service areas. In an implementation, afterdetermining that the buyer payment service belongs to the first servicearea, the first area user identifier of the first buyer in the firstservice area can be determined. In an example implementation, themultiple area user identifiers associated with the first domain-wideuser identifier of the first buyer and the corresponding multipleservice areas can be queried based on the domain-wide platform usermodel and the first domain-wide user identifier of the first buyer, andthen it can be queried whether the multiple service areas include thefirst service area. If the multiple service areas include the firstservice area, the first area user identifier corresponding to the firstservice area is determined based on a mapping relationship between themultiple service areas and the multiple area user identifiers. If themultiple service areas do not include the first service area, a new useridentifier is created as the first area user identifier, and acorrespondence between the first area user identifier and the firstservice area is added to the mapping relationship between the multipleservice areas and the multiple area user identifiers. In anotherimplementation, the corresponding first area user identifier can befurther determined after it is determined that the first buyer islocated in the first service area. In an example implementation, thelocation element information of the first buyer can be obtained inresponse to the login success operation, the order submission operation,the interface browsing operation, etc., of the user, so as to determinethat the first buyer is located in the first service area and determinethe first area user identifier of the first buyer in the first servicearea. Based on this, the first area user identifier can be obtained.

As described herein, it can be determined that the to-be-processed buyerpayment service belongs to the first service area based on the paymentrequest. In addition, the first buyer has the first area user identifierin the first service area. In addition, it can be determined, based onthe above setting of the sites in the service platform, that the areasite (referred to as the first area site in the present specification)corresponding to the first service area includes the buyer service site(referred to as the first buyer service site in the presentspecification) configured to process buyer services in the first servicearea.

Therefore, step S430 can be performed to route the buyer payment serviceto the first buyer service site, for the first buyer service site toprocess the buyer payment service through interconnection with thepayment channel and interconnection with the first buyer based on thefirst area user identifier, and to locally store the service datagenerated by the processing the buyer payment service.

It should be noted that interconnection with the user and the paymentchannel in the buyer payment service can be implemented using theexisting technologies. Interconnecting with the first buyer based on thefirst area user identifier means identifying the first buyer using thefirst area user identifier in the process of interconnection with thefirst buyer, so as to store service data related to the first buyer andfacilitate subsequent access and invocation. Local storage means storagein the first service area, because the first service area is localrelative to the first buyer service site. For example, the service datacan be stored in the first buyer service site, or can be stored in alocal database outside the site. In addition, in an implementation, ifdata related to the first area user identifier has been stored in thefirst buyer service site, service data newly generated by the buyerpayment service can be associated and stored. In another implementation,if the first area user identifier does not exist in multiple area useridentifiers stored in the first buyer service site, the first area useridentifier is added to the multiple area user identifiers.

For ease of understanding, the buyer payment service is brieflydescribed. Processing of the buyer payment service mainly includes:interconnecting with the payment channel so that a system of the paymentinstitution corresponding to the payment channel performs a deductionoperation on a payment account of the first buyer in the payment channelbased on a to-be-paid amount of the first order, and transfers thededucted amount to a financial account of the service platform. Itshould be understood that subsequently, the service platform performssettlement with the first seller based on a subsequent processingsituation of the first order.

As described herein, the buyer payment service can be routed to thefirst buyer service site, for the first buyer service site to processthe buyer payment service. Further, the payment success messagecorresponding to the payment request can be obtained in step S440.

In an implementation, after successfully performing the deductionoperation on the first buyer, the system of the payment institutionsends the payment success message to the first buyer service site.Correspondingly, this step can include: receiving, by the serviceplatform, the payment success message from the first buyer service site.In another implementation, after successfully performing the deductionoperation on the first buyer, the system of the payment institution cansend the payment success message to the first buyer service site and theservice platform at the same time. Correspondingly, this step caninclude: receiving the payment success message from the system of thepayment institution.

Above, the payment success message can be obtained. In step S450, it isdetermined that the to-be-processed seller delivery service belongs tothe second service area based on the payment success message. The placeof registration of the first seller is located in the second servicearea. In an implementation, this step can include: determining that theplace of registration of the first seller is located in the secondservice area based on the payment success message; and furtherdetermining the second service area as the service area the sellerdelivery service belongs to. In another implementation, this step canfurther include: determining the second service area corresponding tothe first seller based on a pre-established mapping relationship betweena seller and a service area.

In still another implementation, before step S450, the second servicearea corresponding to the first seller can be determined. For example,the second service area corresponding to the first seller is determinedin response to the creation of the first order or in response to thepayment request of the first order. Correspondingly, in this step, thesecond service area previously determined can be directly obtained andused as the service area the seller delivery service belongs to.

It can be seen from the setting of the sites in the service platformthat the area site (referred to as the second area site in the presentspecification) corresponding to the second service area includes theseller service site (referred to as the second seller service site inthe present specification). In an implementation, step S450 can bereplaced with determining that the to-be-processed seller deliveryservice belongs to the second seller service site for processing basedon the payment success message. In an implementation, the second sellerservice site corresponding to the first seller can be determined basedon the pre-established mapping relationship between a seller and aseller service site.

As described herein, it can be determined that the to-be-processedseller delivery service belongs to the second service area, and it canbe determined that the second area site corresponding to the secondservice area includes the second seller service site. Further, in stepS460, the seller delivery service can be routed to the second sellerservice site, for the second seller service site to process the sellerdelivery service through interconnection with the first seller, and tolocally store service data generated by the processing the sellerdelivery service. It should be noted that in an implementation, a siteresponsible for processing the seller delivery service can bealternatively determined as the second seller service site in this step.In addition, interconnection with the first seller in the sellerdelivery service can be implemented using the existing technologies. Assuch, the seller delivery service can be routed, so that the secondseller service site processes the seller delivery service throughinterconnection with the first seller.

Through implementation of steps S410 to S460, cross-domain serviceprocessing can be implemented. In one situation, the first service areaand the second service area are different areas, and the correspondingoverall service is a cross-domain (cross-area) service. In anothersituation, the first service area and the second service area can be thesame area, so that intra-domain (intra-area) service processing can beimplemented. In summary, the previously described service processingmethod supports processing of intra-domain services and cross-domainservices, facilitating unified management of all the services.

It should be noted that in an implementation, after step S460, themethod can further include: routing an order settlement servicecorresponding to the first seller to the second seller service site, forthe second seller service site to process the order settlement servicethrough interconnection with the second seller, and to locally storeservice data generated by the processing the order settlement service.It should be noted that the order settlement service mainly includes thefollowing: the service platform transfers the payment of the order thathas arrived to the corresponding seller. In an example implementation,routing the order settlement service can be triggered in multiple ways,for example, receiving a receipt confirmation message for the firstorder from the first buyer service site, or receiving the receiptconfirmation message from the user terminal of the first buyer, orrouting the order settlement service in response to automatic triggeringof a period (e.g., one week or one month) specified for the ordersettlement service. As such, the order settlement service can be routed,so that the second seller service site processes the order settlementservice.

In addition, as described above, through the previously describedservice processing method, the user can view full data of the user, andaccurate recommendation can be made to the user by using the full data,so the user experience is improved.

For example, the multiple service areas associated with the several areaidentities of the first buyer correspond to multiple area sites.Therefore, in an implementation, after step S460, the method can furtherinclude: in response to an order viewing instruction sent by the firstbuyer, querying order information of multiple orders associated with themultiple area user identifiers from the multiple area sites for viewingby the first buyer, where the multiple orders include the first order.As such, orders in each service area can be viewed together.

In an implementation, before step S410, the method can further include:querying multiple historical orders associated with the multiple areauser identifiers from the multiple area sites; and recommending aproduct to the first buyer based on purchased products included in themultiple historical orders. As such, a user can be assisted in locatinga target product, for example, the product included in the first order.

In conclusion, according to the service processing method disclosed inthis implementation of the present specification, a user can useservices provided by global sellers by registering with the serviceplatform only once while it is ensured that service data meetsregulatory constraints, and a seller and a payment channel can be reusedby global users or global buyers by accessing the service platform onlyonce. As such, this can undoubtedly improve user experience greatly andeffectively promote service development.

In addition, it should be noted that through implementation of theservice processing method, a multi-channel payment service of one orderand a pool purchase service of multiple users can be furtherimplemented. The pool purchase service means supporting multiple usersin submitting one order together. In addition, multiple channels canbelong to different service areas, and multiple users can also belong todifferent service areas. In an implementation, a user selects paymentchannel A (an account balance is 10 yuan) and payment channel B (anaccount balance is 20 yuan) for the payment of an order of an amount of29 yuan. Payment channel A corresponds to service area A and paymentchannel B corresponds to service area B. In this case, the buyer paymentservice can be split into two buyer payment services, which are routedto buyer service site A corresponding to service area A and buyerservice site B corresponding to service area B respectively, so that thetwo buyer service sites interconnect with payment channel A and paymentchannel B respectively to process one of the buyer payment services,thereby completing payment of the order. Similarly, for multiple users,an area identity corresponding to each user can be determined, and thenthe buyer payment service is split into multiple buyer services, whichare routed to corresponding buyer service sites for processingrespectively. As such, the service platform can implement multi-channelpayment services and cross-domain user pool purchase services.

According to an aspect, an implementation of the present specificationfurther discloses a service processing method. In the service processingmethod, a service platform determines a to-be-processed service. Whendetermining that the service belongs to a buyer service, the serviceplatform routes the service to a buyer service site in a correspondingarea for processing. When determining that the service belongs to aseller service, the service platform routes the service to a sellerservice site in a corresponding area for processing.

For example, FIG. 5 is a schematic flowchart illustrating a serviceprocessing method according to another implementation. The serviceprocessing method is performed by a service platform. For example, theservice platform includes multiple area sites corresponding to multipleservice areas, and each area site includes a corresponding buyer servicesite and seller service site.

As shown in FIG. 5, the method can include the following steps:

Step S510: Determine that a first service currently needs to beperformed. Further, on one hand, step S520 and step S530 may beperformed, detailed as follows: Step S520: When it is determined thatthe first service needs to be processed through interconnection with afirst buyer, determine a first buyer service site corresponding to afirst service area that the first buyer belongs to. The first buyercorresponds to a first domain-wide user identifier and has a first areaidentity in the first service area, which is determined based onmultiple area user identifiers associated with the first domain-wideuser identifier. Step S530: Route the first service to the first buyerservice site, for the first buyer service site to process the firstservice through interconnection with the first buyer based on the firstarea user identifier, and to locally store service data generated by theprocessing the first service. On the other hand, step S540 and step S550may be performed, detailed as follows: Step S540: When it is determinedthat the first service needs to be processed through interconnectionwith a first seller, determine a second seller service sitecorresponding to a second service area that the first seller belongs to.A place of registration of the first seller is located in the secondservice area. Step S550: Route the first service to the second sellerservice site, for the second seller service site to process the firstservice through interconnection with the first seller, and to locallystore service data generated by the processing the first service.

The previously described steps are, for example, illustrated as follows:

First, in step S510, it is determined that the first service currentlyneeds to be processed. For example, in an implementation, the serviceplatform can determine a service for corresponding processing based onan operation of a user or a seller in the service platform. In anotherimplementation, the service platform can determine a correspondingto-be-processed service based on a message sent by a site included inthe service platform and with reference to predetermined service logic.In still another implementation, the service platform can automaticallytrigger service processing based on certain predetermined periodicservices (e.g., an order settlement service between the service platformand a seller).

Based on this, in an example implementation, the first service is abuyer payment service. Correspondingly, this step can include:determining that the buyer payment service currently needs to beprocessed in response to a payment request initiated by the first buyerfor a first order. The payment request includes a selected paymentchannel.

In an example implementation, the first service is a seller deliveryservice. Correspondingly, this step can include: determining that theseller delivery service currently needs to be processed in response toreceiving a payment success message for a first order. The first orderincludes a product provided by the first seller.

As such, it can be determined that the first service currently needs tobe processed.

It should be noted that the service platform provides services forbuyers and sellers. Correspondingly, the services to be processed can beservices that need to interconnect with buyers, services that need tointerconnect with sellers, or other services that do not need tointerconnect with buyers or the sellers. Service transactions betweenthe buyer and the seller are implemented by using the service platformas an intermediate site. Therefore, any transaction between the buyerand the seller can be split into a seller service that needs tointerconnect with the buyer and a seller service that needs tointerconnect with the seller.

Correspondingly, it is determined whether the first service belongs to abuyer service or a seller service. In an implementation, multiple buyerservices and multiple seller services can be determined based on theservice content of the platform, and then used for matching of the firstservice. In other words, the first service certainly falls into themultiple buyer services or the multiple seller services if the firstservice is a service that the buyer or the seller needs to participatein. In an example implementation, the multiple buyer services caninclude an order creation service, an order buyer payment service, and apersonal information change service. In an example implementation, theseller services can include a new product launch (launching a newproduct in a platform store) service, a seller delivery service, and anorder settlement service.

In an implementation, each service has execution logic of the service.Correspondingly, it can be directly determined whether the first serviceneeds to interconnect with the buyer or the seller based on servicelogic of the first service.

Based on this, after it is determined that the first service currentlyneeds to be processed, on one hand, step S520 and step S530 may beperformed. For example, in an implementation, the first service is thebuyer payment service. Therefore, step S520 can include: determining,based on predetermined multiple buyer services that need to interconnectwith users, that the multiple buyer services include the buyer paymentservice; and then determining that the first service area that the firstbuyer belongs to corresponds to the first buyer service site. A place ofregistration of a payment institution corresponding to the paymentchannel is located in the first service area. Further, step S530 caninclude: routing the buyer payment service to the first buyer servicesite, for the first buyer service site to process the buyer paymentservice through interconnection with the payment channel andinterconnection with the first buyer based on the first area useridentifier, and to locally store service data generated by theprocessing the buyer payment service.

On the other hand, step S540 and step S550 may be performed. Forexample, in an implementation, the first service is the seller deliveryservice. Therefore, step S540 can include: determining, based onpredetermined multiple seller services that need to interconnect withsellers, that the multiple seller services include the seller deliveryservice. Further, step S550 can include: routing the seller deliveryservice to the second seller service site, for the second seller servicesite to process the seller delivery service through interconnection withthe first seller, and to locally store service data generated by theprocessing the seller delivery service.

In addition, it should be noted that for the description of the steps inFIG. 5, references can also be made to the related description of thesteps in FIG. 4. Details are omitted for simplicity.

In conclusion, according to the service processing method disclosed inthis implementation of the present specification, a user can useservices provided by global sellers by registering with the serviceplatform only once while ensuring that service data meets regulatoryconstraints, and a seller and a payment channel can be reused by globalusers or global buyers by accessing the service platform only once. Assuch, this can undoubtedly improve user experience greatly andeffectively promote service development.

Corresponding to the service processing method disclosed in thepreviously described implementation, an implementation of the presentspecification further discloses a service processing apparatus. Detailsare as follows:

FIG. 6 is a schematic structural diagram illustrating a serviceprocessing apparatus according to an implementation. The apparatus isintegrated into a service platform, the service platform includesmultiple area sites corresponding to multiple service areas, and eacharea site includes a corresponding buyer service site and seller servicesite. As shown in FIG. 6, an apparatus 600 includes: a payment requestreceiving unit 601, configured to receive a payment request initiated bya first buyer for a first order, the first buyer corresponding to afirst domain-wide user identifier, a product in the first order beingprovided by a first seller, and the payment request including a selectedpayment channel; a first area determining unit 602, configured todetermine a first service area that a buyer payment servicecorresponding to the payment request belongs to, a first area sitecorresponding to the first service area including a first buyer servicesite, the first buyer having a first area user identifier in the firstservice area, which is determined based on multiple area useridentifiers associated with the first domain-wide user identifier, and aplace of registration of a payment institution corresponding to thepayment channel being located in the first service area; a paymentservice routing unit 603, configured to route the buyer payment serviceto the first buyer service site, for the first buyer service site toprocess the buyer payment service through interconnection with thepayment channel and interconnection with the first buyer based on thefirst area user identifier, and to locally store service data generatedby the processing the buyer payment service; a payment successacquisition unit 604, configured to obtain a payment success messagecorresponding to the payment request; a second area determining unit605, configured to determine that a to-be-processed seller deliveryservice belongs a second service area based on the payment successmessage, a place of registration of the first seller being located inthe second service area, and a second area site corresponding to thesecond service area including a second seller service site; and adelivery service routing unit 606, configured to route the sellerdelivery service to the second seller service site, for the secondseller service site to process the seller delivery service throughinterconnection with the first seller, and to locally store service datagenerated by the processing the seller delivery service.

In an implementation, the apparatus 600 further includes: a domain-wideidentifier determining unit 607, configured to determine the firstdomain-wide user identifier corresponding to the first buyer in responseto the successful login of the first buyer; and an order creation unit608, configured to create the first order in response to receiving anorder creation request initiated by the first buyer based on theproduct.

In an implementation, the domain-wide identifier determining unit 607is, for example, configured to obtain a user name of the first buyer;and perform a hash operation on the user name to obtain the firstdomain-wide user identifier; or query the first domain-wide useridentifier based on a pre-established mapping relationship between auser name and a domain-wide user identifier.

In an implementation, the apparatus 600 further includes: a locationelement acquisition unit 609, configured to obtain location elementinformation of the first buyer; a buyer area determining unit 610,configured to determine a service area in which the first buyer iscurrently located based on the location element information, and use theservice area as the first service area; an area identifier determiningunit 611, configured to determine the first area user identifier of thefirst buyer in the first service area based on the multiple area useridentifiers corresponding to multiple service areas; and a candidatechannel acquisition unit 612, configured to obtain multiple candidatepayment channels for selection by the first buyer, where places ofregistration of payment institutions corresponding to the multiplecandidate payment channels are all located in the first service area.

In an example implementation, the location element information includesat least one of longitude and latitude information, a network address,an IP address, and a consignee address included in the first order.

In an example implementation, the area identifier determining unit 611is, for example, configured to create a new user identifier as the firstarea user identifier when a user identifier corresponding to the firstservice area does not exist in the multiple area user identifiers; andclassify the first area user identifier into the multiple area useridentifiers.

In an implementation, the first area determining unit 602 is, forexample, configured to determine a place of registration correspondingto the payment channel, and use a service area in which the place ofregistration is located as the first service area.

In an example implementation, the apparatus 600 further includes an areaidentifier determining unit 611, configured to determine the first areauser identifier of the first buyer in the first service area based onthe multiple area user identifiers corresponding to multiple serviceareas.

In an implementation, the second area determining unit 605 is configuredto determine a place of registration of the first seller based on thepayment success message, and use a service area in which the place ofregistration is located as the second service area.

In an implementation, the apparatus 600 further includes a settlementservice routing unit 613, configured to route an order settlementservice corresponding to the first seller to the second seller servicesite, for the second seller service site to process the order settlementservice through interconnection with the second seller, and to locallystore service data generated by the processing the order settlementservice.

In an implementation, the apparatus 600 further includes an orderviewing processing unit 614, configured to: in response to an orderviewing instruction sent by the first buyer, query order information ofmultiple orders associated with the multiple area user identifiers fromthe multiple area sites for viewing by the first buyer, where themultiple orders include the first order.

In an implementation, the apparatus 600 further includes a productrecommendation unit 615, configured to query multiple historical ordersassociated with the multiple area user identifiers from the multiplearea sites; and recommend a product to the first buyer based onpurchased products included in the multiple historical orders.

In conclusion, according to the service processing apparatus disclosedin this implementation of the present specification, a user can useservices provided by global sellers by registering with the serviceplatform only once while it is ensured that service data meetsregulatory constraints, and a seller and a payment channel can be reusedby global users or global buyers by accessing the service platform onlyonce. As such, this can undoubtedly improve user experience greatly andeffectively promote service development.

FIG. 7 is a schematic structural diagram illustrating a serviceprocessing apparatus according to another implementation. An apparatus700 is integrated into a service platform, the service platform includesmultiple area sites corresponding to multiple service areas, and eacharea site includes a corresponding seller service site and buyer servicesite. As shown in FIG. 7, the apparatus 700 includes:

a service determining unit 710, configured to determine that a firstservice currently needs to be processed; a buyer site determining unit720, configured to determine, when it is determined that the firstservice needs to be processed through interconnection with a firstbuyer, a first buyer service site corresponding to a first service areathat the first buyer belongs to, the first buyer corresponding to afirst domain-wide user identifier and having a first area identity inthe first service area, which is determined based on multiple area useridentifiers associated with the first domain-wide user identifier; abuyer service routing unit 730, configured to route the first service tothe first buyer service site, for the first buyer service site toprocess the first service through interconnection with the first buyerbased on the first area user identifier, and to locally store servicedata generated by the processing the first service; a seller sitedetermining unit 740, configured to determine, when it is determinedthat the first service needs to be processed through interconnectionwith a first seller, a second seller service site corresponding to asecond service area that the first seller belongs to, a place ofregistration of the first seller being located in the second servicearea; and a seller service routing unit 750, configured to route thefirst service to the second seller service site, for the second sellerservice site to process the first service through interconnection withthe first seller, and to locally store service data generated by theprocessing the first service.

In an implementation, the first service is a buyer payment service; andthe service determining unit 710 is, for example, configured todetermine that the buyer payment service currently needs to be processedin response to a payment request initiated by the first buyer for afirst order, where the payment request includes a selected paymentchannel; the buyer site determining unit 720 is, for example, configuredto determine, based on predetermined multiple buyer services that needto interconnect with buyers, that the multiple buyer services includethe buyer payment service; and determine the first buyer service sitecorresponding to the first service area that the first buyer belongs to,where a place of registration of a payment institution corresponding tothe payment channel is located in the first service area; and the buyerservice routing unit 730 is, for example, configured to route the buyerpayment service to the first buyer service site, for the first buyerservice site to process the buyer payment service throughinterconnection with the payment channel and interconnection with thefirst buyer based on the first area user identifier, and to locallystore service data generated by the processing the buyer paymentservice.

In an implementation, the first service is a seller delivery service;and the service determining unit 710 is, for example, configured todetermine that the seller delivery service currently needs to beprocessed in response to a payment success message for a first order,where the first order includes a product provided by the first seller;and the seller site determining unit 740 is, for example, configured todetermine, based on predetermined multiple seller services that need tointerconnect with sellers, that the multiple seller services include theseller delivery service.

In conclusion, according to the service processing apparatus disclosedin this implementation of the present specification, a user can useservices provided by global sellers by registering with the serviceplatform only once while it is ensured that service data meetsregulatory constraints, and a seller and a payment channel can be reusedby global users or global buyers by accessing the service platform onlyonce. As such, this can undoubtedly improve user experience greatly andeffectively promote service development.

An implementation of still another aspect further provides acomputer-readable storage medium storing computer programs. A computerperforms the method described in FIG. 4 or FIG. 5 when the computerprograms are executed on the computer.

An implementation of still another aspect further provides a computingdevice, including a memory and a processor. The memory stores executablecode, and the processor implements the method described in FIG. 4 orFIG. 5 when executing the executable code.

A person skilled in the art should be aware that in the previous one ormore examples or functions described in the multiple implementationsdisclosed in the present specification can be implemented by hardware,software, firmware, or any combination thereof. When the functions areimplemented by software, the functions can be stored in acomputer-readable medium or transmitted as one or more instructions orcode in the computer-readable medium.

The objectives, technical solutions, and benefits of the multipleimplementations disclosed in the present specification are furtherdescribed in detail in the above example implementations. It should beunderstood that the above descriptions are merely exampleimplementations of the multiple implementations disclosed in the presentspecification, but are not intended to limit the protection scope of themultiple implementations disclosed in the present specification. Anymodification, equivalent replacement, or improvement made on the basisof the technical solutions of the multiple implementations disclosed inthe present specification shall fall within the protection scope of themultiple implementations disclosed in the present specification.

The various embodiments described above can be combined to providefurther embodiments. Aspects of the embodiments can be modified, ifnecessary, to employ concepts of the various embodiments to provide yetfurther embodiments.

These and other changes can be made to the embodiments in light of theabove-detailed description. In general, in the following claims, theterms used should not be construed to limit the claims to the specificembodiments disclosed in the specification and the claims, but should beconstrued to include all possible embodiments along with the full scopeof equivalents to which such claims are entitled. Accordingly, theclaims are not limited by the disclosure.

What is claimed is:
 1. A method, comprising: deploying a plurality ofservers for implementing a plurality of area sites of a serviceplatform, the plurality of area sites respectively corresponding to aplurality of geographic regions, the plurality of geographic regions notoverlapping with one another, a server of each area site of theplurality of area sites physically located in a geographic regioncorresponding to the area site and configured to interconnect with aservice in the geographic region and to locally store data generatedthrough the interconnection with the service in the geographic region;assigning, by the service platform, a first domain-wide user identifierand a first plurality of area user identifiers to a first buyer, thefirst plurality of area user identifiers each linked to the firstdomain-wide user identifier and corresponding to a respective area siteof the plurality of area sites; assigning, by the service platform, asecond domain-wide user identifier and a second plurality of area useridentifiers to a first seller, the second plurality of area useridentifiers each linked to the second domain-wide user identifier andcorresponding to a respective area site of the plurality of area sites;receiving a payment request initiated by the first buyer for a firstorder, a product in the first order being provided by the first seller,and the payment request including a selected payment channel;determining that a buyer payment service corresponding to the paymentrequest belongs to a first geographic region, a first area site of theplurality of area sites corresponding to the first geographic regionincluding a first buyer service site, the first buyer having a firstarea user identifier for the first area site, the first geographicregion being determined based on a place of registration of a paymentinstitution corresponding to the selected payment channel being locatedin the first geographic region; and routing the buyer payment servicecorresponding to the first order to the first buyer service site, forthe first buyer service site to process the buyer payment servicethrough interconnection with the selected payment channel andinterconnection with the first buyer based on the first area useridentifier of the first buyer, and to locally store at the first areasite service data generated by the processing the buyer payment service.2. The method according to claim 1, further comprising: before thereceiving the payment request initiated by the first buyer for the firstorder, determining the first domain-wide user identifier correspondingto the first buyer in response to a successful login of the first buyer;and creating the first order in response to receiving an order creationrequest initiated by the first buyer.
 3. The method according to claim2, wherein the determining the first domain-wide user identifiercorresponding to the first buyer includes: obtaining a user name of thefirst buyer; and obtaining the first domain-wide user identifier by atleast one of performing a hash operation on the user name or queryingthe first domain-wide user identifier based on an existing mappingrelationship between the user name and the first domain-wide useridentifier.
 4. The method according to claim 2, after the creating thefirst order and before the receiving the payment request initiated bythe first buyer for the first order, further comprising: obtaininglocation element information of the first buyer; determining ageographic region in which the first buyer is currently located based onthe location element information, and using the geographic region as thefirst geographic region; determining the first area user identifier ofthe first buyer in the first geographic region based on the firstplurality of area user identifiers; and obtaining a plurality ofcandidate payment channels for selection by the first buyer, whereinplaces of registration of payment institutions corresponding to theplurality of candidate payment channels are all located in the firstgeographic region.
 5. The method according to claim 4, wherein thelocation element information includes at least one of longitude andlatitude information, a network address, an Internet Protocol (IP)address, and a consignee address included in the first order.
 6. Themethod according to claim 4, wherein the determining the first area useridentifier of the first buyer in the first geographic region based onthe plurality of area user identifiers corresponding to the plurality ofgeographic regions includes: creating a previously presented useridentifier as the first area user identifier in response to a useridentifier corresponding to the first geographic region not existing inthe plurality of area user identifiers; and classifying the first areauser identifier into the plurality of area user identifiers.
 7. Themethod according to claim 1, wherein the determining the firstgeographic region that the buyer payment service corresponding to thepayment request belongs to includes: determining a place of registrationcorresponding to the payment channel, and determining a geographicregion in which the place of registration is located as the firstgeographic region.
 8. The method according to claim 7, furthercomprising: after the determining the first geographic region that thebuyer payment service corresponding to the payment request belongs to,and before the routing the buyer payment service to the first buyerservice site, determining the first area user identifier of the firstbuyer in the first geographic region based on the first plurality ofarea user identifiers.
 9. The method according to claim 1, furthercomprising: before the receiving the payment request initiated by thefirst buyer for the first order, querying a plurality of historicalorders associated with the first plurality of area user identifiers fromthe plurality of area sites; and recommending a product to the firstbuyer based on purchased products included in the plurality ofhistorical orders.
 10. A method, comprising: deploying a plurality ofservers for implementing a plurality of area sites of a serviceplatform, the plurality of area sites respectively corresponding to aplurality of geographic regions, the plurality of geographic regions notoverlapping with one another, a server of each area site of theplurality of area sites physically located in a geographic regioncorresponding to the area site and configured to interconnect with aservice in the geographic region and to locally store data generatedthrough the interconnection with the service in the geographic region;assigning, by the service platform, a first domain-wide user identifierand a first plurality of area user identifiers to a first buyer, thefirst plurality of area user identifiers each linked to the firstdomain-wide user identifier and corresponding to a respective area siteof the plurality of area sites; assigning, by the service platform, asecond domain-wide user identifier and a second plurality of area useridentifiers to a first seller, the second plurality of area useridentifiers each linked to the second domain-wide user identifier andcorresponding to a respective area site of the plurality of area sites;obtaining a payment success message corresponding to a payment requestfor a first order between the first buyer and the first seller, aproduct in the first order being provided by the first seller;determining that a seller delivery service corresponding to the firstorder belongs to a first geographic region, a first area sitecorresponding to the first geographic region including a first sellerservice site, the first seller having a first area user identifier forthe first area site; and routing the seller delivery service to thefirst seller service site, for the first seller service site to processthe seller delivery service through interconnection with the firstseller based on the first area user identifier of the first seller, andto locally store at the first area site service data generated by theprocessing the seller delivery service.
 11. The method according toclaim 10, wherein the determining that the seller delivery servicecorresponding to the first order belongs to the first geographic regionincludes: determining a place of registration of the first seller basedon the payment success message, and determining a geographic region inwhich the place of registration is located as the first geographicregion.
 12. The method according to claim 10, further comprising: afterthe routing the seller delivery service to the first seller servicesite, routing an order settlement service corresponding to the firstseller to the first seller service site, for the first seller servicesite to process the order settlement service through interconnectionwith the first seller, and to locally store service data generated bythe processing the order settlement service.
 13. The method according toclaim 10, further comprising: after the routing the seller deliveryservice to the second seller service site, in response to an orderviewing instruction sent by the first seller, querying order informationof a plurality of orders associated with the second plurality of areauser identifiers from the plurality of area sites for viewing by thefirst seller, wherein the plurality of orders include the first order.14. The method according to claim 10, further comprising: determiningthe second domain-wide user identifier corresponding to the first sellerin response to a successful login of the first seller; and creating thefirst order in response to receiving an order creation request initiatedby the first seller.
 15. The method according to claim 14, wherein thedetermining the second domain-wide user identifier corresponding to thefirst seller includes: obtaining a user name of the first seller; andobtaining the second domain-wide user identifier by at least one ofperforming a hash operation on the user name or querying the seconddomain-wide user identifier based on an existing mapping relationshipbetween the user name and the second domain-wide user identifier. 16.The method according to claim 15, further comprising: obtaining locationelement information of the first seller; determining a geographic regionin which the first seller is currently located based on the locationelement information, and using the geographic region as the firstgeographic region; determining the first area user identifier of thefirst seller in the first geographic region based on the secondplurality of area user identifiers; and obtaining a plurality ofcandidate seller delivery services for selection by the first seller,wherein places of registration of the plurality of candidate sellerdelivery service are all located in the first geographic region.
 17. Themethod according to claim 16, wherein the location element informationincludes at least one of longitude and latitude information, a networkaddress, an Internet Protocol (IP) address, and a consignee addressincluded in the first order.
 18. The method according to claim 16,wherein the determining the first area user identifier of the firstseller in the first geographic region based on the second plurality ofarea user identifiers corresponding to the plurality of geographicregions includes: creating a previously presented user identifier as thefirst area user identifier in response to a user identifiercorresponding to the first geographic region not existing in the secondplurality of area user identifiers; and classifying the first area useridentifier into the second plurality of area user identifiers.
 19. Acomputing device, comprising a memory and a processor, the memorystoring executable instructions, the executable instructions, whenexecuted by the processor, enable the processor to implement actsincluding: deploying a plurality of servers for implementing a pluralityof area sites of a service platform, the plurality of area sitesrespectively corresponding to a plurality of geographic regions, theplurality of geographic regions not overlapping with one another, aserver of each area site of the plurality of area sites physicallylocated in a geographic region corresponding to the area site andconfigured to interconnect with a service in the geographic region andto locally store data generated through the interconnection with theservice in the geographic region, each area site including a buyerservice site and a seller service site; assigning, by the serviceplatform, a first domain-wide user identifier and a first plurality ofarea user identifiers to a first user, the first plurality of area useridentifiers each linked to the first domain-wide user identifier andcorresponding to a respective area site of the plurality of area sites;determining that the first user having the first domain-wide identifierhas logged in for a first service; determining the first plurality ofarea user identifiers of the first user based on the first domain-wideidentifier; and routing the first service to an area site of theplurality of area sites for the area site to process the first serviceusing an area user identifier of the first plurality of area useridentifiers that corresponds to the area site, and to locally store atthe area site service data generated by the processing the firstservice.
 20. The computing device according to claim 19, wherein theacts include: obtaining location element information of the first user;determining a geographic region in which the first buyer is currentlylocated based on the location element information; and determining thearea site based on the geographic region in which the first buyer iscurrently located.